[docker] added some docker files to more easily test dog#90
Draft
dloser wants to merge 1 commit intogizmore:masterfrom
Draft
[docker] added some docker files to more easily test dog#90dloser wants to merge 1 commit intogizmore:masterfrom
dloser wants to merge 1 commit intogizmore:masterfrom
Conversation
Collaborator
|
Nice work, d! |
Collaborator
Author
|
Never really had a need for it myself. I can usually get around fine with #gm commands. But yes, it would useful to have in some cases and could also be used to add some regression tests and such. Shouldn't be to difficult to import via the shell or use the images to make volumes from SQL dumps. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Definitely far from perfect, but quite useful, I suspect.
Basically run build.sh to make images and then run.sh (from docker/), both as root. Probably best to check scripts to adapt to your situation. When running, use 'setup' once to initialize stuff (will give error, but is ok). After that type 'run' to start dog and have it connect the ircd in the container. You can connect yourself as well via exposed port 6667, so you can interact, change code, .die, and 'run' again. Using internal network so Dog can't go connecting to all kinds of servers (as it will try with the current sources).
There are plenty of errors to go around, but Dog seems to work fine. Ultimately it would be best to have better separation of code and config (e.g. OWNER.php, secret.php, GameMasters.php, dog_timer).